Skip to content

Deploy RC 466 to Production#12049

Merged
amirbey merged 10 commits intostages/prodfrom
stages/rc-2025-04-03
Apr 3, 2025
Merged

Deploy RC 466 to Production#12049
amirbey merged 10 commits intostages/prodfrom
stages/rc-2025-04-03

Conversation

@amirbey
Copy link
Copy Markdown
Contributor

@amirbey amirbey commented Apr 3, 2025

User-Facing Improvements

  • Document Authentication: Update language on how to verify your identity works page (#12046)

Bug Fixes

  • Authorization Requests: Fix default AAL overriding specified AAL value (#12044)

Internal

  • IPP testing: Allow immediate approval of pending IPP enrollments in int (LG-16017) (#12014)
  • In-person Proofing: Update the status_check_completed_at enrollment timestamp when an enrollment is skipped during the get_usps_proofing_results_job (#12037)
  • Maintenance: Delete completed Profile backfill classes (#12026)
  • SAML: Validate SAML configuration during application start (#12035)
  • Tech debt: Remove unused phone confirmation database fields (#12013)

Upcoming Features

  • Attempts API: Add events and failure reason handling (#12041)
  • Attempts API: Some enrollment events (#12038)
  • Document Authentication: Fill in id type on choose id type screen if already selected (#12039)

Mitchell Henke and others added 10 commits March 31, 2025 13:20
* Validate SAML configuration during application start

changelog: Internal, SAML, Validate SAML configuration during application start

* add specs
* Allow approving pending IPP enrollments in int

Currently, when testing the IPP flow in the sandbox (int), one must wait 1 to 2
hours before the verification is complete. The sandbox is the environment
that all our partners use to test their apps, and that the Partnerships team
uses to test, and for live demos for partners. Having to wait 1 to 2 hours is a huge blocker.

A few months ago, a feature was built that allows approving pending IPP
enrollments immediately via the /test/ipp route. This feature was originally
built for local development only. This PR seeks to make this feature available
in our deployed hosts as well, via a config setting.

In the process, I made some improvements to the existing feature, such as:

- Add controller and feature tests
- Move the logic that determines whether or not this feature is available to `FeatureManagement`
- Make sure the user is fully authenticated
- When not in local development, only display and update pending enrollments that belong to the current user
- Make queries more robust and performant with `find_by` and avoiding N+1 queries
- In the view, use `size` instead of `count`, since `count` can lead to some issues in some cases (although unlikely in this situation).

changelog: Internal, IPP testing, Allow immediate approval of pending IPP enrollments in int (LG-16017)
* changelog: Upcoming Features, Attempts API, Some enrollment events
* changelog: Upcoming Feature, Attempts API, Add events and failure reason handling
* changelog: Upcoming Features, passport, fill in id type on choose id type screen if already selected

* Fixing controller spec

* Updating spec

* Updated naming convention for passport not selected status

* Updating feature test for standard and mobile flow

* changing radio check name in feature spec

* Updating standard flow and adding hybrid tests
changelog: Internal, Maintenance, Delete completed Profile backfill classes
changelog: Bug Fixes, Authorization Requests, Fix default AAL overriding specified AAL value
* changelog: Internal, Tech debt, Remove unused phone confirmation database fields

* updated schema

* mark phone cofirmed as true

* mark phone confirmed as true in spec

* remove changes to phone_configuration.confirmed_at
…2037)

changelog: Internal, In-person Proofing, Update the status_check_completed_at enrollment timestamp when an enrollment is skipped during the get_usps_proofing_results_job

This commit also enhances the enrollment_skipped event by adding the
response from the USPS API to the event log.
@amirbey amirbey merged commit 63470fc into stages/prod Apr 3, 2025
1 check passed
@amirbey amirbey deleted the stages/rc-2025-04-03 branch April 3, 2025 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants